Refactor persistence commands for DB migration#38
Merged
Conversation
Move server write paths onto command-oriented store operations so file and blob adapters share the same registration, passport, prize, award, and restore behavior. This prepares the persistence seam for Netlify DB and dual-write rollout while preserving current API responses. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
✅ Deploy Preview for kid-a ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Blob-backed read-modify-write paths are making the storage layer hard to migrate safely to Netlify DB. This PR introduces the first migration slice: a command-oriented persistence boundary that preserves current file/blob behavior while giving future DB and dual-write adapters explicit operations to implement.
Summary
Notes for review
Validation
npm run --silent lintnpm run --silent buildnpm run --silent build:server